@Article{CostaCostAgui:2014:LoDaAn,
author = "Costa, Carlos Filipe da Silva and Costa, C{\'e}sar Augusto and
Aguiar, Odylio Denys",
affiliation = "{Universidade de S{\~a}o Paulo (USP)} and {Instituto Nacional de
Pesquisas Espaciais (INPE)} and {Instituto Nacional de Pesquisas
Espaciais (INPE)}",
title = "Low-latency data analysis for the spherical detector Mario
Schenberg",
journal = "Classical and Quantum Gravity",
year = "2014",
volume = "31",
number = "8",
keywords = "gravitational waves, astrophysical events.",
abstract = "The confrontation of gravitational waves (GWs) with their
electromagnetic (EM) counterparts will be rich with information
about astrophysical events. Initially, this confrontation will
corroborate GW detections; afterwards, when GW detections become
more recurrent, it will allow astrophysics to combine information
from different channels (GW, EM and also neutrinos). A low-latency
data analysis which provides the direction of an incoming GW
candidate is required to confront it with fast follow-up EM
observations. Until now, no low-latency data analysis has been
developed for spherical detectors. One spherical detector alone is
capable of determining both the GW direction and polarization. By
using this capability, we have developed a low-latency data
analysis pipeline for the Mario Schenberg detector. This pipeline
is able to retrieve the direction of GW triggers with an average
angular resolution from \δs ~ 8° at SNR ~ 12 to \δs ~
1° at SNR ~ 80, in a timespan of a 4 s for 32 s of data being
analyzed. We apply a veto which reduces fake events up to 90% when
maintaining the GW efficiency above 90% for high SNRs. We provide
here a description of the method and its efficiency: resolution on
the direction, false alarm rate and computational time.",
doi = "10.1088/0264-9381/31/8/085012",
url = "http://dx.doi.org/10.1088/0264-9381/31/8/085012",
issn = "0264-9381",
label = "scopus 2014-05 CostaCostAgui:2014:LoDaAn",
language = "en",
targetfile = "Low_Latency_Mario_Schenberg_rev.pdf",
urlaccessdate = "02 maio 2024"
}